-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: use ilpy.expressions in motile Constraints #30
Conversation
I wonder if we shouldn't make the return value of
for node, selection_indicator in selection_indicators.items():
# use selection_indicator here assumes less familiarity with the internals than for node, index in selection_indicators.items():
# know what to do with an index |
Codecov Report
❗ Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more. @@ Coverage Diff @@
## main #30 +/- ##
==========================================
- Coverage 92.77% 92.47% -0.30%
==========================================
Files 30 30
Lines 747 718 -29
==========================================
- Hits 693 664 -29
Misses 54 54
|
This is now ready for review @funkey |
Perfect, looks all good. Thanks a lot! |
This updates most of the motile constraints and costs to use
ilpy.Expression
introduced in funkelab/ilpy#9 and released in ilpy v0.3.0Another notable (API breaking) change is that indexing into a Variable (i.e.
Variable.__get_item__
) now returns anilpy.Variable
instance, rather than an integer, as per #30 (comment). In many cases, thatVariable
can be used exactly as the integer could before (it can be cast to an int withint()
, it can be used as an index in aSolution
, etc...), but it can also be used to create expressions.